MuleSoft Accelerator for Salesforce Service Cloud

v1.5

12 February 2021

Functional changes

• Use of the Common Scheduler has been replaced with local schedulers in some APIs to simplify configuration and deployment
• Migrated our custom Lightning Web Component for Order History to a more generic one, which enhances it for greater usability

API specification updates

• An Accelerator version of the Cloud Information Model (CIM) library has been introduced, along with a CIM Extensions library
• A get:/orders endpoint was added to the OMS System API
• The Jira Experience API now has a proper RAML-defined model
• All API specifications have been updated to use more consistent naming and design patterns while maintaining backwards-compatibility

Documentation updates

• Runtime properties that must be overridden are now documented for each implementation template
• Diagrams and documentation for several use cases have been updated to reflect processing changes

Other updates

• The OData example API has been updated to access order data via the OMS System API instead of having a direct database connection
• The OMS System API itself was simplified to use an out-of-the-box configuration of Apache OFBiz as a sample back end
• The Order Export Cartridge was updated to use a clearer filename format
• Module and connector dependencies have been updated to latest released versions

v1.4

23 December 2020

Functional changes

• Addition of health check endpoint to all APIs
• HTTPS protocol now enabled by default
• Improved retry handling overall to skip certain errors
• Additional enhancements to some processing flows
• Enhanced CloudHub deployment configuration

Other updates

• Improved documentation for Customer Sync cartridge installation and configuration
• Implementation templates upgraded to Mule 4.3.x and Studio 7.7.x
• Enhanced MUnit and Postman tests
• Updated according to latest MuleSoft Fingerprint Analyzer rules
• Better overall alignment with Technical Best Practices

v1.3

30 October 2020

Functional changes

• Order History (Service Cloud <- OMS): OMS database was replaced with Apache OFBiz from a generic database (updated).
• Added support for Client ID enforcement to all APIs.

Ease of use updates

• Simplified build and deployment by referencing parent POM and Common Core library as Exchange dependencies.
• Separated build and deployment scripts from parent POM into a separate resource.
• Broke monolithic build script into separate scripts for Common Services, Service Cloud, and Commerce Cloud builds.
• Also included a build script for the Service Cloud <-> Jira for use case 2 (create issues or incidents) and use case 3 (updates to issues or incidents).
• Migrated PDF-based setup and reference architecture guides to individual Exchange overview and asset pages.
• Separated Service Cloud vs. Commerce Cloud overview pages.
• Created Postman collection to configure required Anypoint MQ resources, which can be found here.

API specification improvements

• Simplified use of multiple fragments by creating a single shared library.
• Removed unnecessary data type definitions from all definitions.
• Asset name change for consistency: qualified all accelerator components with "Accelerator". This will also be reflected in the Exchange asset IDs, "accelerator-" for API specifications, and "accel-" for implementation templates.
• Removed displayName tags on endpoints for better clarity in Exchange.

Other updates

• Upgraded Anypoint connectors and Mule modules to the latest supported versions.

v1.2

17 July 2020

Documentation

• Set-up guide v1.2
• Reference architecture v1.2

Change summary

The focus of release 1.2 is on increasing ease of use and enhancing developer experience.

• NEW: Commerce Cloud use cases (Commerce Cloud - use cases 3 & 4 in the reference architecture)
  • Order creation/capture: B2C Commerce -> Order Management System (OMS): Taking orders created in B2C Commerce and pushing them to an external OMS.
    • Export schedule is set in B2C Commerce by the administrator user.
  • Order status update: OMS -> B2C Commerce: Keeping B2C Commerce updated with the status of an order, pulled from an external OMS.
    • An administrator sets the schedule for export of order status to B2C Commerce
• UPDATED: Common component -- Notification service: Slack notification was added.
• UPDATED: All templates were updated with the most current connectors.

v1.1

24 April 2020

Documentation

• Set-up guide v1.1
• Reference architecture v1.1

Change summary

The focus of release 1.1 is on increasing ease of use and enhancing developer experience.

• NEW: Scripts for building and deploying all Accelerator assets, in the right order, to simplify and accelerate deployment. Each script is ready to run except for configuration values - look for the string "REPLACE_BY_USER"; all such values are mandatory and must be set to legitimate values to get a useful result.
  • The parent-POM project will build all components of the Accelerator suite, automatically in the right order
  • Included: Bash and Windows scripts to build and deploy all applications with one command.
  • Included: Bash and Windows scripts with each project to deploy that project alone. Building projects individually is possible but take care to use the parent-POM to build everything if any child components (eg. core services) are changed.
• NEW: Apart from SAP proprietary JARs (which we cannot distribute), the assets in the Accelerator are self-contained; there is no need to download and install anything else. Once the SAP JARs appropriate for your platform are acquired and installed, one Maven command will build all the APIs in one step.
• UPDATED: All templates were updated with the most current connectors.

*Note: Salesforce topic-listener API was not upgraded

• UPDATED: Outbound connectors are all configured with retry. Retry-configuration is externalized.
• UPDATED: All configuration values for connectors are externalized as before. To enable rapid configuration, password-encryption has been removed. All passwords/secrets are configured using hidden properties for CloudHub deployments.Out-of-the-box configuration within the connector simplifies deployments to CloudHub.
• REMOVED: JSONLogger has been removed. While a helpful resource, we deemed the Accelerator can function optimally without it.

Users who want to use or are already using JSONLogger can easily do so by replacing the standard Logger with JSONLogger and configuring it as desired.

v1.0

30 January 2020

Documentation

• Set-up guide v1.0
• Reference architecture v1.0